PNT Configurable Bit Security Events

Two PNT Security Events relate to the way configurable bits are handled in the PNT Service. The CFGBITxx event and the CBxxdtps event each work in combination with both the ACCESS and ALARMSET events to potentially increase or decrease a user’s permissions to see or modify the properties associated with specific configurable bits. The events in the form of CFGBITxx can only increase a user’s security permissions but the events in the form of CBxxdtps can both increase or decrease a user’s security permissions. User permissions associated with these events are only enforced within the PNT Editor dialog when it is invoked from CygNet Studio or Canvas screens or to the COM API exposed through the CxPnt.dll. In contrast, invoking the PNT Editor from CygNet Explorer or one of the CygNet Utility applications will disable the enforcement of a user’s config-bit specific security permissions related to these events.

Note: If a CFGBITxx event that exists for a status bit conflicts with a CBxxdtps event, the permission and behavior indicated by the CBxxdtps event supersedes the CFGBITxx event.

CFGBITxx Event

The CFGBITxx event (where xx represents the zero-padded bit number: Config Bit 01 - Config Bit 15) allows access to point record configurable bit properties for Analog, Digital, Enumeration, and String point types. This event can only increase a user's security privileges from what is established by ACCESS and ALARMSET events. Permissions set on a specific CFGBITxx event will never decrease a user’s access to the properties of the specific configurable bit.

The CFGBITxx event format is displayed below:

CFGBIT<xx> (eight character maximum)

CBxxdtps Event

The CBxxdtps event controls access to who can see and edit specific configurable bit setting properties for Analog, Digital, Enumeration, and String point types. This event can increase or decrease a user's security privileges from what is established by ACCESS and ALARMSET events.

Note: When a user has no configured association to an existing CBxxdtps event, that user's access will resolve to NONE.

The CBxxdtps event can optionally be qualified by point type (dt) and Point Scheme (ps) to account for when configurable bits change their meanings across point types and Point Schemes. As an example, for the event "CB01AN01", user permission of "2-Update" would allow a user to edit the setpoint value for the status bit associated with Config Bit 01 for Analog Input/Output points for Point Scheme 1.

The CBxxdtps event format is displayed below:

CB<xx><dt><ps> (eight character maximum)

Examples

Back to top